|
This page last changed on Apr 09, 2008.
The following table describes available options for each operation you have selected to import.
Options Available for Imported Web Service Operations
Characteristic |
Options |
Comment |
Operation |
adjust as needed |
You can change the nominated name to any legal XML name using the built-in line editor. |
Public |
Boolean |
By default Web service-derived operations are protected. A checkbox allows you to mark any function or procedure as public. (Once in a data service, operations can be marked private as needed.) |
Kind |
- Read
- Create
- Update
- Delete
- Library function
- Library procedure
|
Operations determined to return void are automatically marked as library procedures.
You can change the nominated function type. The wizard attempts to correctly set the function type being imported.
 | Operations marked as create, update, or delete functions will be packaged in an Entity data service. Otherwise, the resulting data service will be of type Library. | |
Primary |
Boolean |
Not applicable for web service operations. |
Root Element |
Root element of the operation |
For complex data types the topmost element is listed. In case of RPC-style web services the top-most generated element is listed. |
| Target Namespace |
imported value |
This represents the target namespace of the generated data service. |
Setting Characteristics of Imported Web Service Operations

|